1. Home
  2. Vulnerabilities
  3. CVE-2022-50367
0.0
NA
CVE-2022-50367
fs: fix UAF/GPF bug in nilfs_mdt_destroy
Description

In the Linux kernel, the following vulnerability has been resolved: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode() returns true and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(), which frees the uninitialized inode->i_private and leads to crashes(e.g., UAF/GPF). Fix this by moving security_inode_alloc just prior to this_cpu_inc(nr_inodes)

INFO

Published Date :

Sept. 17, 2025, 3:15 p.m.

Last Modified :

Sept. 17, 2025, 3:15 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2022-50367 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Fix a kernel bug where inode initialization could lead to crashes.
  • Apply the kernel patch to correct inode handling.
  • Update the Linux kernel to a patched version.
  • Reboot the system after applying updates.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2022-50367.

URL Resource
https://git.kernel.org/stable/c/1e555c3ed1fce4b278aaebe18a64a934cece57d8
https://git.kernel.org/stable/c/2a96b532098284ecf8e4849b8b9e5fc7a28bdee9
https://git.kernel.org/stable/c/2e488f13755ffbb60f307e991b27024716a33b29
https://git.kernel.org/stable/c/64b79e632869ad3ef6c098a4731d559381da1115
https://git.kernel.org/stable/c/70e4f70d54e0225f91814e8610477d65f33cefe4
https://git.kernel.org/stable/c/81de80330fa6907aec32eb54c5619059e6e36452
https://git.kernel.org/stable/c/c0aa76b0f17f59dd9c9d3463550a2986a1d592e4
https://git.kernel.org/stable/c/d1ff475d7c83289d0a7faef346ea3bbf90818bad
https://git.kernel.org/stable/c/ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2022-50367 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2022-50367 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2022-50367 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2022-50367 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 17, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode() returns true and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(), which frees the uninitialized inode->i_private and leads to crashes(e.g., UAF/GPF). Fix this by moving security_inode_alloc just prior to this_cpu_inc(nr_inodes)
    Added Reference https://git.kernel.org/stable/c/1e555c3ed1fce4b278aaebe18a64a934cece57d8
    Added Reference https://git.kernel.org/stable/c/2a96b532098284ecf8e4849b8b9e5fc7a28bdee9
    Added Reference https://git.kernel.org/stable/c/2e488f13755ffbb60f307e991b27024716a33b29
    Added Reference https://git.kernel.org/stable/c/64b79e632869ad3ef6c098a4731d559381da1115
    Added Reference https://git.kernel.org/stable/c/70e4f70d54e0225f91814e8610477d65f33cefe4
    Added Reference https://git.kernel.org/stable/c/81de80330fa6907aec32eb54c5619059e6e36452
    Added Reference https://git.kernel.org/stable/c/c0aa76b0f17f59dd9c9d3463550a2986a1d592e4
    Added Reference https://git.kernel.org/stable/c/d1ff475d7c83289d0a7faef346ea3bbf90818bad
    Added Reference https://git.kernel.org/stable/c/ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.